Skip to content

feat: Add multi-repo switching support with server backend integration#148

Closed
Rocky0102 wants to merge 3 commits into
abhigyanpatwari:mainfrom
Rocky0102:fix/web-backend-multi-repo-switching
Closed

feat: Add multi-repo switching support with server backend integration#148
Rocky0102 wants to merge 3 commits into
abhigyanpatwari:mainfrom
Rocky0102:fix/web-backend-multi-repo-switching

Conversation

@Rocky0102

Copy link
Copy Markdown

Fixed problem: when use web UI to connect to backend server (4747 port), cypher query and AI chat not working, reporting KuzuDB error/repo not loaded.

  • Add currentRepoName state tracking in useAppState for repo context
  • Update initializeAgent to accept overrideRepoName parameter for server mode
  • Implement server-mode query execution with repo parameter in runQuery
  • Fix HTTP endpoint paths in ingestion worker (remove duplicate /api prefix)
  • Increase agent recursion limit from 50 to 200 for complex multi-step reasoning
  • Pass repo context through App.tsx handleServerConnect callback

Enables seamless switching between multiple indexed repositories when connected to a server backend, with proper repo context propagation through query execution and agent initialization.

- Add currentRepoName state tracking in useAppState for repo context
- Update initializeAgent to accept overrideRepoName parameter for server mode
- Implement server-mode query execution with repo parameter in runQuery
- Fix HTTP endpoint paths in ingestion worker (remove duplicate /api prefix)
- Increase agent recursion limit from 50 to 200 for complex multi-step reasoning
- Pass repo context through App.tsx handleServerConnect callback

Enables seamless switching between multiple indexed repositories when connected to a server backend, with proper repo context propagation through query execution and agent initialization.
@vercel

vercel Bot commented Mar 3, 2026

Copy link
Copy Markdown

@srocky2035-hash is attempting to deploy a commit to the NexusCore Team on Vercel.

A member of the Team first needs to authorize it.

- Implement resizable left/right panels with ResizableDivider component
  - Left panel (file tree): 200-600px range
  - Right panel (code/chat): 400-800px range

- Add per-repo chat session management with server-side persistence
  - Sessions organized by repository (repoName field)
  - Auto-save sessions on task completion
  - Save sessions before clearing or switching repos
  - Load/delete/refresh session functionality per repo
  - Store sessions in separate files: ~/.gitnexus/sessions/{repoName}.json
  - No quantity limit - all sessions per repo are preserved
  - Add backend API endpoints: GET/POST/DELETE /api/sessions

- Preserve tool call args in UI display
  - Add args property to ToolCallInfo type
  - Display tool arguments in ToolCallCard component
@Rocky0102

Copy link
Copy Markdown
Author

Second Commit:
feat: add resizable panels and per-repo chat session persistence

  • Implement resizable left/right panels with ResizableDivider component

    • Left panel (file tree): 200-600px range
    • Right panel (code/chat): 400-800px range
  • Add per-repo chat session management with server-side persistence

    • Sessions organized by repository (repoName field)
    • Auto-save sessions on task completion
    • Save sessions before clearing or switching repos
    • Load/delete/refresh session functionality per repo
    • Store sessions in separate files: ~/.gitnexus/sessions/{repoName}.json
    • No quantity limit - all sessions per repo are preserved
    • Add backend API endpoints: GET/POST/DELETE /api/sessions
  • Preserve tool call args in UI display

    • Add args property to ToolCallInfo type
    • Display tool arguments in ToolCallCard component

2. session history: save separately by repo with individual files per session
3. rename Clear button to New to better reflect starting a new session
@magyargergo

Copy link
Copy Markdown
Collaborator

⚠️ Upcoming Prettier formatting — rebase instructions

PR #563 adds Prettier as the code formatter for the repo. When it merges, the bulk format commit will touch ~350 files (style-only: whitespace, quotes, trailing commas). Your branch will likely conflict.

After #563 merges, rebase your branch:

git fetch origin
git checkout <your-branch>
git rebase origin/main

# Conflicts will be formatting-only — accept your version:
git checkout --theirs .
git add .
git rebase --continue

# Then re-format your branch to match the new style:
npx prettier --write .
git add -A
git commit -m "style: apply prettier formatting"
git push --force-with-lease

New setup step: Run npm install at the repo root (not just in gitnexus/) to get prettier + activate the pre-commit hook. The hook auto-formats staged files on every commit going forward.

@magyargergo

Copy link
Copy Markdown
Collaborator

Please submit a new PR if this is still relevant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants